Repository navigation
CI: move actions to their Node 24 releases - #4
Merged
Merged
Conversation
GitHub is forcing Node 20 actions onto Node 24 and annotating every run with a deprecation warning. All inputs this workflow passes exist unchanged in the new majors. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps checkout, setup-python, setup-node and upload-artifact to v7, setup-buildx-action to v4, and build-push-action to v7. Every input the workflow uses exists unchanged in the new versions. This removes the Node 20 deprecation warnings from every CI run.
🤖 Generated with Claude Code